Unified management method of various types of messages of a personal information terminal

ABSTRACT

A mobile terminal includes a display and a controller. The display outputs a first input window configured to receive a first message. When input data is received into at least one message field of the first input window, the controller determines whether or not the input data conforms to a format of the first input window corresponding to the first message. The controller also outputs a notification after the input is determined not to conform to the format corresponding to the first input window corresponding to the first message. The display outputs a second input window to receive a second message. The second input window has at least one message field different from the message fields in the first input window.

This is a Continuation of U.S. patent application Ser. No. 12/559,834filed Sep. 15, 2009, which is a Continuation of U.S. patent applicationSer. No. 10/118,943 filed Apr. 10, 2002, which claims the benefit of theKorean Application Nos. 01-19389 and 01-19390 filed Apr. 11, 2001, andKorean Patent Application No. 01-21910 filed Apr. 24, 2001, thedisclosures of where are incorporated herein by reference.

BACKGROUND

1. Field

One or more embodiments herein relate to electronic messaging.

2. Background

Remarkable technology development is making a cellular phone and a PCSphone much smaller, lighter and cheaper, so that a mobile phone is beingpopularized widely and rapidly. In these days, various mobileinformation terminals other than the popularized mobile phone are beingintroduced too. Among those mobile information terminals, a PDA(Personal Digital Assistant) stands in the spotlight of consumers.

Some PDAs equip with a CDMA wireless modem which can communicate signalswith a CDMA mobile communication network, thus, a person carrying such aPDA is able to use a mobile communication network or to communicate datathrough a mobile communication network anytime and anywhere. In otherwords, a user with such a PDA can use not only Short Message Service(SMS) of a mobile communication network but also data communication suchas e-mail transmitting/receiving through traffic channels allocated inair link of a mobile communication network.

However, the SMS of a mobile communication network and the e-mailservice of a data network are totally different each other in protocol.Namely, the SMS uses a protocol specified by a mobile communicationnetwork whereas the e-mail service uses Post Office Protocol(POP)/Simple Mail Transfer Protocol (SMTP) agreed with a data server.Because the SMS and the e-mail service are conducted according to themutually different protocols, the PDA has in general two built-inmessage management (editing, displaying, transmitting, etc.) applicationprograms, one for message to be received/transmitted through SMS whichis called ‘SMS message’ hereinafter, and the other for message to bereceived/transmitted through e-mail service which is called ‘mailmessage’ hereinafter. Thus, two separate DBs are prepared for SMSmessages and mail ones respectively.

However, users do not know well the fact that the SMS message and themail message exist separately due to such technical differences.Instead, they feel only inconvenience of message management becausethere are two separate methods which conduct same function, namely,message delivery. For example, when a user completes a SMS message, itcan not be transmitted if it is against SMS protocol, e.g., if an e-mailaddress is entered as a recipient's address. In this case, a mailmanagement application program should be executed newly. Then, becausethe application program to send a message is changed, the previouslyentered message is not preserved. Therefore, a user should re-write thesame message or copy and paste the previous message into the mailmanagement application program. This procedure to correct protocolmismatched inputs is somewhat boring to a user.

Moreover, a user also feels boring in message storing and searching workbecause of two separate methods of same function. Namely, if a user cannot remember exactly whether a message he or she wrote is a SMS or amail one, same message searching operations would be conductedindividually with the two message-related applications.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the present invention, illustrate the preferredembodiments of the invention, and together with the description, serveto explain the principles of the present invention, and wherein:

FIG. 1 is a block diagram of one embodiment of a personal informationterminal conducting a unified management method of plural types ofmessages;

FIG. 2 is a flow chart of an embodiment of displaying received messagesall together regardless of their types in accordance with a unifiedmessage management method of a personal information terminal;

FIG. 3 shows a format of a unified message management table;

FIG. 4 shows a list of two types of messages displayed all together;

FIG. 5 shows an example of arrangement conditions for two types ofmessages displayed all together in a list;

FIGS. 6 a and 6 b are flow charts of an embodiment of selecting messagetransmitting manner suitable to the type of a written message inaccordance with a unified message management method of a personalinformation terminal;

FIG. 7 shows a ‘New Mail’ input screen in which a warning window askingto switch to ‘New Memo’ is popped up when a recipient field is filled inwith a telephone number;

FIG. 8 is an illustrative ‘New Memo’ input screen of which recipientfield is filled in with an e-mail address;

FIG. 9 is an illustrative ‘New Memo’ input screen in which a warningwindow asking to transmit through e-mail service when the size ofwritten message is beyond limit; and

FIG. 10 is a flow chart of an embodiment of providing an input screensuitable for a message to write and transmitting a written message inaccordance with a unified message management method of a personalinformation terminal.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of one embodiment of a personal informationterminal conducting a unified management method of various types ofmessages. The personal information terminal of FIG. 1 comprises an I/Omodule 10 for inputting/outputting data; a storage module 40 for storingseveral DBs or data tables; a communicating module 30 for conductingdata communication; and a controlling module 20 for controlling datainput/output, data conversion, and data communication.

In details, the I/O module 10 includes a wide LCD 11 for displayinginformation and a touch screen 12 for data input, the communicatingmodule 30 includes a signal transceiver 31 transmitting/receivingwireless signals; a WAP unit 32 conducting WAP (Wireless ApplicationProtocol) which ensures reliability of wireless data communication; anda SMS unit 33 allocating/extracting SMS messages to/from signalchannels, and the controlling module 20 includes a message type checkingunit 21 checking which type a written message belongs to; a message typeconverting unit 22 converting the format of a written message to matchto other type based on whether it is matched with its intended type; aPOP3/SMTP unit 23 formatting a mail message to the e-mail protocol andretrieving a mail message vice versa; a WAP format adapting unit 24adapting a POP/SMTP-formatted message to wireless transmissionconditions and decoding received wireless signals to obtain digitaldata; a SMS format adapting unit 25 adapting a message to SMS protocoland retrieving a SMS message from the received wireless signals; and acontrolling unit 26 supervising operations of all elements overall.

FIG. 2 is a flow chart of an embodiment of displaying received messagesall together regardless of their types of a personal informationterminal in accordance with a unified message management method. Theprocedure of FIG. 2 conducted in the personal information terminal ofFIG. 1 is explained below in detail.

First, the controlling unit 26 displays a variety of built-inapplication programs and menu items onto the wide LCD 11 to be selectedby a user (S10).

If a user clicks a unified receipt box among displayed items (S11), thecontrolling unit 26 searches both a mail message DB 42 and a SMS messageDB 43 having been created in the storage module 40. All messages storedin the two DBs 42 and 43 have been received from outside. The twoseparate DBs 42 and 43 may be integrated into one DB.

In addition, a unified message management table (UMMT) 41 has beencreated in the storage module 40. The UMMT 41 is used for unifiedmanagement of the two DBs 42 and 43 which contain different types ofmessages, respectively.

FIG. 3 shows the format of the UMMT 41. The fields of an entry of theUMMT 41 are compose of ‘Message ID’ identifying a message uniquely,‘Date/Time’ indicative of date and time when a message is received (forreceipt box) or transmitted (for transmitted box), ‘Type/Opened’indicative of message type and whether a message is opened or not,‘Receiver’ and ‘Sender’ in which addresses of receiver and sender arefilled in respectively, ‘Title’ in which title of a mail message iswritten or full or partial SMS message is written, and ‘Size’ indicativeof the size of an actual message.

The ‘Message ID’ links each entry of the UMMT 41 with a correspondingactual message written in the mail message DB 42 or the SMS message DB43. The ‘Date/Time’, name of ‘Receiver’ or ‘Sender’, ‘Title’,‘Type/Opened’ field may be used for arranging condition.

The controlling unit 26 sequentially reads all entries of the UMMT 41,configured as above, stored in the storage module 40, and lists all or apart of them within a single window on the wide LCD 11, as shown in FIG.4 (S12). At this time, the controlling unit 26 does not refer the mailmessage DB 42 and the SMS message DB 43 when it displays only title fora mail message and a short part of message for a SMS message. However,it reads out contents of respective messages from the two DBs 42 and 43with reference to the message IDs written in each ‘Message ID’ field ofthe UMMT 41 when it has to show mail message and SMS message fully.

Specific fields are expressed differently based on message type. Forexample, information written in ‘Sender’ field is expressed in the formof e-mail address when the message type is mail, and in the form oftelephone subscriber number when the type is SMS.

In the meantime, the controlling unit 26 may insert different icons withdifferent color, which are determined based on the information writtenin ‘Type/Opened’ field, before every displayed items in the message listas shown in FIG. 4, as a result, a user can easily recognize whichmessages are not read yet and which type they belong to.

Afterwards, if the user selects ‘Arrange’ menu item (S13) in thecondition that main menu of the unified receipt box is opened, thecontrolling unit 26 pops up a sub-menu composed of arrangementconditions of title, name (address) of receiver/sender, date/time, andmessage type, as shown in FIG. 5 (S14). If the user chooses one of thearrangement conditions (S15,S17,S19,S21) the messages in the list arere-arranged in ascending or descending alphanumeric order with respectto the chosen field (S16,S18,S20,S22).

The type arrangement condition may have sub-arrangement condition of‘Opened’ which determines which one of unread messages and opened onesis displayed first. Through the above-explained method, a user can checkall messages by listing messages once irrespective of their types.

FIGS. 6 a and 6 b are flow charts of an embodiment of selecting messagetransmitting manner suitable to the type of a written message in apersonal information terminal in accordance with a unified messagemanagement method. The procedure of FIGS. 6 a and 6 b conducted in thepersonal information terminal of FIG. 1 are explained below in detail.

First, the controlling unit 26 checks which application item is selectedthrough the touch screen 12 by a user (S40). If a ‘New Mail’ item ischosen by the user (S41) because an e-mail is intended to send, thecontrolling unit 26 provides an initial screen for a new mail whichincludes ‘To’, ‘CC’, ‘Attached’, ‘Title’ field, and message input window701, as shown in FIG. 7 (S42). Then, the user fills in the ‘To’ and the‘Title’ with respective necessary information without exception andfills in the ‘CC’ and the ‘Attached’ field, if needed. Afterwards, theuser writes a message to send in the message input window 701. Throughthese filling-in works, a mail message to send is completed (S43).

When the user requests for transmission of the completed mail message(S44), the controlling unit 26 commands the message type checking unit21 to verify the completed message. The message type checking unit 21examines the data written in the ‘To’ field (S45). If the data writtenin the ‘To’ field includes a symbol ‘@’, indicative of mail account, aswell as alphanumeric characters (S46), the message type checking unit 21delivers the completed message to the message type converting unit 22while informing the message type converting unit 22 that the message isformat-matched and requesting no-conversion of message type at the sametime. Then, the message type converting unit 22 only delivers thereceived message to the POP3 unit 23 without type conversion. Thecompleted message sent to the POP3 unit 23 is formatted to the mailprotocol and transmitted to a target mail server through a wireless link(S47).

If the data written in the ‘To’ field is composed of numeric digits notincluding the symbol of ‘@’ (S50), the message type checking unit 21informs the controlling unit 26 of the fact. Then, the controlling unit26 pops up a warning window 710 which informs of impossible messagedelivery of the completed message through e-mail service and asks theuser to change delivery manner of the completed mail message (S51), asshown in FIG. 7.

If the user agrees to type converted delivery by clicking ‘OK’ button onthe warning window 710, the controlling unit 26 commands the messagetype converting unit 22 to convert the completed message received fromthe message type checking unit 21 to a SMS-formatted message. Then,before delivering the received message to the SMS format adapting unit25, the message type converting unit 22 slices the written message intosuitable-sized ones, which will be individually sent to the SMS formatadapting unit 25 like as an independent SMS message, if the messagelength is beyond the limit of one message, and it composes a stringindicative of filename and full pathname of an attached file if a fileis attached in the ‘Attached’ field and appends the composed string tothe written message, and it also adds a text in the ‘Title’ before thebody message.

The SMS format adapting unit 25 adds necessary header and additionalinformation to the completed message or the respective sliced messagesin accordance with SMS protocol. The SMS-formatted message or messagesare transmitted to a remote mobile phone through a wireless link (S52).

If a ‘New Memo’ item is chosen for SMS message transmission by the user(S60) instead of ‘New Mail’, the controlling unit 26 provides an initialscreen for a new memo which includes ‘To’, ‘From’, and a message inputwindow 801 onto the wide LCD 11, as shown in FIG. 8 (S61). At this time,the ‘From’ field may be omitted. If omitted, a subscriber number havingbeen stored in an internal memory by the user is appended to a writtenmemo by the SMS format adapting unit 25 to form a complete SMS message.

If the user requests for transmission of a written memo (S63) afterfilling in each field in an input screen of FIG. 8 with respectivenecessary information (S62), the message type checking unit 21 examinesthe data written in the ‘To’ field (S64) as explained above. If the datawritten in the ‘To’ field includes only numeric digits (S65), thecompleted memo is delivered to the SMS format adapting unit 25 whichtransmits it to a remote side (S66) after formatting to a SMS message.

However, if the data written in the ‘To’ field includes the symbol of‘@’ indicative of a mail account (S70) as shown in FIG. 8 thecontrolling unit 62 pops up a warning window which informs of impossiblemessage delivery of the completed memo through SMS and asks the user tochange delivery manner of the completed SMS message to e-mail service(S71).

If the user agrees to type converted delivery the message typeconverting unit 22 conducts conversion of the written SMS message toe-mail format, namely, it creates ‘CC’ and ‘Attached’ fieldadditionally, writes null data in those fields respectively, anddelivers the field-added message to the POP3/SMTP unit 23. The POP3 unit23 formats the field-added message to the mail protocol and thentransmits it to a mail server of a recipient via a WAP unit 32 (S72).

In the above procedures of memo composition and transmission thereof,even though the user fills in the ‘To’ field with proper numeric digitsthe controlling unit 26 may not transmit the written memo in the form ofSMS message. Instead, the following additional verification andprocedures based on the result of the verification may be conducted.

The message type checking unit 21 further counts alphanumeric characterswritten in the message input window 801 of FIG. 8, even though the ‘To’field is filled in with proper numeric data, and informs the countedsize of the memo to the controlling unit 26. Then, the controlling unit26 checks whether the informed size is beyond the maximum size, e.g., 50bytes allowed in a single SMS message. If below the maximum size, thecontrolling unit 26 makes the written memo be sent in the form of SMSmessage.

If the counted size is greater than the maximum size, the controllingunit 26 outputs a warning message 101 which informs that the writtenmemo is preferable to be sent through e-mail service and asks the userwhether he or she wants to switch the current ‘New Memo’ to ‘New Mail’screen, as shown in FIG. 9. If the user still wants the written memo inthe form of SMS message, the controlling unit 26 slices the written memointo maximum-sized messages allowable in SMS and sends each of thesliced messages to the SMS format adapting unit 25 one by one throughthe message format converting unit 22. The sliced SMS-formatted messagesare transmitted sequentially to a target terminal addressed by the ‘To’field.

If the user wants to switch the input screen to ‘New Mail’, thecontrolling unit 26 searches a mapping table 44 of telephone number toe-mail address, which is pre-stored in the storage module 40 by theuser, for the numeric digits filled in the ‘To’ field. If found, thecontrolling unit 26 copies the e-mail address associated with the foundnumeric digits of the mapping table 44 to the ‘To’ field of thenewly-activated ‘New Mail’. The controlling unit 26 conducts sameoperations for the ‘From’ field of the ‘New Memo’ and, if the numericdigits in the ‘From’ field are found in the mapping table 44, it sendsan e-mail address associated with the found numeric digits to the POP3unit 23 which will add the received originating e-mail address to thewritten message in accordance with the e-mail protocol.

If the numeric digits are not found in the mapping table 44, acorresponding field in the ‘New Mail’ screen is left blank in order thatthe user might fill in with proper e-mail address manually.

Through the above-explained method, a user can send a SMS message aswell as a mail message through ‘New Mail’ screen and send a mail messageas well as a SMS message through ‘New Memo’ screen, too. Therefore, auser need not confirm in advance which type a message to write belongsto in order to choose a suitable one of ‘New Mail’ for e-mail messageand ‘New Memo’ for SMS message.

In the meantime, the controlling unit 26 also outputs an informativemessage telling “Please correct the automatically-substituted e-mailaddress if it is not correct”.

If the user requests for transmission of the written message in thecondition that all fields are filled in properly, the written message istransmitted in the form of e-mail message to a mail server of arecipient through processes explained in detail above.

In the case that the written message in the ‘New Memo’ screen istransmitted in the form of e-mail message as aforementioned because itslength is too long to encapsulate into a SMS message, the controllingunit 26 composes an additional short SMS message, e.g., a phrase of“E-mail transmitted to you” destined for the subscriber number writtenin the ‘To’ field of the ‘New Memo’ and sends it to the SMS formatadapting unit 25 to be delivered to same recipient. The reason why theadditional SMS message is composed and sent is to make a recipient checkthe transmitted e-mail message as soon as possible because it isintended to be sent in the form of SMS message which can be acknowledgedmore promptly than the e-mail message.

FIG. 10 is a flow chart, conducted in a personal information terminal,of an embodiment of determining the type of a message to write,providing an input screen suitable for the determined message type, andtransmitting a message written the provided input screen in accordancewith a unified message management method.

In the procedure of FIG. 10, the controlling unit 26 outputs an inputwindow demanding only information of a recipient (S80) first when a userrequests for a new message. After data is entered in the input windowcompletely, the controlling unit 26 commands the message type checkingunit 21 to examine the entered data (S81). The message type checkingunit 21 regards a message to write as SMS message when the entered datais composed of numeric digits, and as mail message when the entered dataincludes the symbol of ‘@’ indicative of a mail account (S82). Theidentified message type by the message type checking unit 21 is notifiedto the controlling unit 26. Then, the controlling unit 26 provides the‘New Mail’ screen of FIG. 7 if identified as mail message and the ‘NewMemo’ screen of FIG. 8 if identified as SMS message (S83,S88). At thistime, the controlling unit 26 copies the data entered in the inputwindow to the ‘To’ field of the message input screen of FIG. 7 or 8.

After the user completes a message by filling in necessary informationas well as a body message in fields of the message input screen(S84,S89) he or she requests for transmission of the completed message(S85,S90). Then, the message type converting unit 22 delivers thecompleted message to the POP3/SMTP unit 23 or the SMS format adaptingunit 25 which will transmit the received message to a remote side inaccordance with a protocol intended by ‘New Mail’ or ‘New Memo’(S86,S91).

Owing to the above-explained method, there is no need that a user shouldchoose a message input screen suitable for a message type to transmit.

The above-explained unified message management method of a personalinformation terminal makes a user confirm all types of received messagesat a time and removes user's inconvenience that a message type to writeshould be distinguished in advance prior to choosing a message inputscreen.

It is one object to provide a unified message management method of apersonal information terminal which displays plural types of messagesall together through a single window, and transmits a completed messageafter matching it to a protocol determined based on information writtenin its field distinguishing a message type.

A unified management method of plural types of messages in a personalinformation terminal where each type has different message field setfrom others is characterized in that it comprises the steps of receivingand storing messages each type of which belongs to the plural types;composing unified management information including information writtenin fields of each of the stored messages; and displaying the storedplural types of messages all together with reference to the composedunified management information.

Another unified management method of plural types of messages in apersonal information terminal where each type has different messagefield set from others is characterized in that it comprises the steps ofreading information on a receiver of a written message of which type isintended to belong to one of the plural types; checking whether or notthe read receiver information is matched with said one type; convertingthe written message to other type different from said one type based ona result of said checking step; and transmitting the type-convertedmessage.

Another unified management method of plural types of messages in apersonal information terminal where each type has different messagefield set from others is characterized in that it comprises the steps ofchecking whether or not a written message, of which type is intended tobelong to one type among the plural types, satisfies conditionsspecified by said one type; converting the written message to other typedifferent from said one type if at least one condition is not satisfied;and transmitting the type-converted message.

Any reference in this specification to “one embodiment,” “anembodiment,” “example embodiment,” etc., means that a particularfeature, structure, or characteristic described in connection with theembodiment is included in at least one embodiment of the invention. Theappearances of such phrases in various places in the specification arenot necessarily all referring to the same embodiment. Further, when aparticular feature, structure, or characteristic is described inconnection with any embodiment, it is submitted that it is within thepurview of one skilled in the art to effect such feature, structure, orcharacteristic in connection with other ones of the embodiments. Thefeatures of any one embodiment may be combined with features of one ormore other embodiments.

Although embodiments of the present invention have been described withreference to a number of illustrative embodiments thereof, it should beunderstood that numerous other modifications and embodiments can bedevised by those skilled in the art that will fall within the spirit andscope of the principles of this invention. More particularly, reasonablevariations and modifications are possible in the component parts and/orarrangements of the subject combination arrangement within the scope ofthe foregoing disclosure, the drawings and the appended claims withoutdeparting from the spirit of the invention. In addition to variationsand modifications in the component parts and/or arrangements,alternative uses will also be apparent to those skilled in the art.

1. A mobile terminal, comprising: a display configured to: display afirst input window configured to receive a first type message, whereinthe first input window comprises a first window identifier and at leastone first message field, the first window identifier indicative of atype of the first input window, display a second input window configuredto receive a second type message, wherein the second input windowcomprises a second window identifier and at least one second messagefield, the second window identifier indicative of a type of the secondinput window, and a controller configured to: determine, when input datais received into at least one first message field of the first inputwindow, whether the input data conforms to a format of the second inputwindow corresponding to the second type message, output a notificationafter the input data is determined to conform to the format of thesecond input window corresponding to the second type message, andconverting information of the first input window into the format of thesecond input window corresponding to the second type message, whereinthe first and second input windows are displayed on the display.
 2. Themobile terminal of claim 1, wherein the format of the second inputwindow that corresponds to the second type message includes informationthat is not included in the first input window.
 3. The mobile terminalof claim 1, wherein the converted information includes the input datareceived into the at least one first message field of the first inputwindow.
 4. The mobile terminal of claim 1, wherein the convertedinformation is not output on the display.
 5. The mobile terminal ofclaim 1, wherein the format of the second input window corresponds to acommunication protocol.
 6. The mobile terminal of claim 1, furthercomprising: a transmitter to transmit the converted information based ona protocol corresponding to the second input window without displayingthe converted information on the display.
 7. The mobile terminal ofclaim 1, wherein the first input window is provided for sending a SMSmessage and the second input window is provided for sending an emailmessage.
 8. The mobile terminal of claim 1, wherein: the at least onefirst message field includes a message address field, and the controlleris to check whether input data received in the message address fieldincludes a predetermined symbol used for the second type message inorder to determine whether the input data conforms to the format of thesecond type message.
 9. The mobile terminal of claim 8, wherein thecontroller is to check whether input data received in the messageaddress field includes an alphanumeric character in order to determinewhether at least one of the input data conforms to a format of thesecond type message.
 10. A mobile terminal, comprising: a display todisplay a first input window configured to receive a first message,wherein the first input window comprises a plurality of first messagefields; and a controller configured to determine, when input data isreceived into at least one of the first message fields of the firstinput window, whether the input data does not conform to a formatcorresponding the first input window corresponding to the first message,and output a notification after the input is determined not to conformto the format corresponding to the first input window corresponding tothe first message, wherein the display is to display a second inputwindow configured to receive a second message, wherein the second inputwindow comprises at least one second message field different from the atleast one first message field.
 11. The mobile terminal of claim 10,wherein the first message includes information for sending at least oneof a SMS message or an email message.
 12. The mobile terminal of claim10, wherein the plurality of the message fields includes a messageaddress field, and wherein the controller is configured to display thenotification when the input data for the message address field isdetermined to include an alphanumeric character.
 13. The mobile terminalof claim 10, wherein: the plurality of the message fields includes amessage address field, the controller is configured to check whetherinput data received in the message address field includes analphanumeric character for the determination.
 14. A method forcontrolling a mobile terminal, comprising: displaying a first inputwindow configured to receive a first type message, wherein the firstinput window comprises a first window identifier and at least one firstmessage field, the first window identifier indicative of a type of thefirst input window; receiving input data into at least one first messagefield of the first input window; determining whether the input dataconforms to a format of a second input window corresponding to a secondtype message; outputting a notification after the input data isdetermined to conform to the format of the second input windowcorresponding to the second type message, wherein second input windowcomprises a second window identifier and at least one second messagefield; and converting information of the first input window into theformat of the second input window corresponding to the second typemessage, wherein the first and second input windows are displayed on thedisplay at different times.
 15. The method of claim 14, wherein theformat of the second input window that corresponds to the second typemessage includes information that is not included in the first inputwindow.
 16. The method of claim 14, wherein the converted informationincludes the input data received into the at least one first messagefield of the first input window.
 17. The method of claim 14, wherein theconverted information is not output on a display.
 18. The method ofclaim 14, wherein the format of the second input window corresponds to acommunication protocol.
 19. The method of claim 14, wherein theconverted information is transmitted based on a protocol thatcorresponds to the second input window without displaying the convertedinformation on a display
 20. The method of claim 14, wherein the firstinput window is provided for sending one of an SMS message or an emailmessage and the second input window is provided for sending the other ofthe SMS message or the email message.
 21. The method of claim 14,wherein: the at least one first message field includes a message addressfield, and said determining comprises checking whether input datareceived in the message address field includes a predetermined symbolused for the second type message.
 22. The method of claim 21, whereinsaid determining comprises: checking whether input data received in themessage address field includes an alphanumeric character.
 23. A methodfor controlling a mobile terminal, comprising: displaying a first inputwindow configured to receive a first message and comprising a pluralityof first message fields; receiving input data into at least one of thefirst message fields of the first input window; determining whether theinput data does not conform to the at least one first message field, andoutputting a notification after the input data is determined not toconform to the first message field; and displaying a second input windowconfigured to receive a second message and comprising at least onesecond message field different from the plurality of first messagefields, wherein the first and second input windows are displayed atdifferent times.
 24. The method of claim 23, wherein the first inputwindow is for sending one of an SMS message or an email message and thesecond input window is for sending the other of an SMS message or anemail message.
 25. The method of claim 23, wherein the plurality of themessage fields includes a message address field, and wherein outputtingthe notification is performed when input data received in the messageaddress field includes an alphanumeric character.
 26. The method ofclaim 23, wherein: the plurality of the message fields includes amessage address field, said determining comprises checking whether inputdata for the message address field includes an alphanumeric character.27. A mobile terminal, comprising: a display; a first input windowconfigured to receive a first message, wherein the first input windowcomprises a plurality of first message fields; a controller configuredto: determine, when input data is received into at least one of thefirst message field of the first input window, whether at least one ofthe input data does not conform to a corresponding first message field,and output a notification to change the input window based on thedetermination; and a second input window configured to receive a secondmessage, wherein the second input window comprises at least one secondmessage field, the at least one first message field different from atleast one second message field, wherein the first and second inputwindows are output on the display of the mobile terminal.
 28. The mobileterminal of claim 27, wherein the first message includes information forsending at least one of a SMS message or an email message.
 29. Themobile terminal of claim 27, wherein the plurality of the message fieldsincludes a message address field, and wherein the controller is furtherconfigured to display the notification when at least one of the inputdata for the message address field is determined to include analphanumeric character.
 30. The mobile terminal of claim 27, wherein theplurality of the message fields includes a message address field, andwherein the controller is further configured to check whether input datareceived in the message address field includes an alphanumeric characterfor the determination.